Reduced size configuration interface

ABSTRACT

An electronic device displays at least one device initialization screen. After displaying the at least one device initialization screen, the electronic device displays an instruction screen instructing a user to pair the external device with the electronic device. The electronic device sends first data via wireless communication, displays a pattern comprising identifying information of the electronic device, and receives second data indicating that the external device and the electronic device have been paired using the first data. After receiving the second data, the electronic device provides an aural or haptic indication that the electronic device and the external device have been paired. In some examples, the electronic device is a wearable electronic device and the external device is a smartphone. Pairing the electronic device and the external device may allow the devices to exchange information and operate interactively with one another.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/407,584, entitled “REDUCED SIZE CONFIGURATION INTERFACE,” filed May9, 2019, which is a continuation of U.S. patent application Ser. No.15/366,607, entitled “REDUCED SIZE CONFIGURATION INTERFACE,” filed Dec.1, 2016, which is a continuation of U.S. patent application Ser. No.14/839,913, entitled “REDUCED SIZE CONFIGURATION INTERFACE,” filed Aug.28, 2015, which claims the benefit of U.S. Provisional PatentApplication Ser. No. 62/044,956, entitled “REDUCED SIZE CONFIGURATIONINTERFACE,” filed Sep. 2, 2014, and U.S. Provisional Patent ApplicationSer. No. 62/129,910, entitled “REDUCED SIZE CONFIGURATION INTERFACE,”filed Mar. 8, 2015, the contents of which are hereby incorporated byreference in their entirety.

This application also relates to the following provisional applications:U.S. Patent Application Ser. No. 62/005,793, entitled “CompanionApplication for Activity Cooperation,” filed May 30, 2014; and U.S.Patent Application Ser. No. 62/005,751, entitled “Predefined WirelessPairing,” filed May 30, 2014; the contents of which are herebyincorporated by reference in their entirety.

This application also relates to the following applications:International Patent Application Serial No. PCT/US2013/040087, entitled“Device, Method, and Graphical User Interface for Moving a UserInterface Object Based on an Intensity of a Press Input,” filed May 8,2013; International Patent Application Serial No. PCT/US2013/040072,entitled “Device, Method, and Graphical User Interface for ProvidingFeedback for Changing Activation States of a User Interface Object,”filed May 8, 2013; International Patent Application Serial No.PCT/US2013/040070, entitled “Device, Method, and Graphical UserInterface for Providing Tactile Feedback for Operations Performed in aUser Interface,” filed May 8, 2013; International Patent ApplicationSerial No. PCT/US2013/040067, entitled “Device, Method, and GraphicalUser Interface for Facilitating User Interaction with Controls in a UserInterface,” filed May 8, 2013; International Patent Application SerialNo. PCT/US2013/040061, entitled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013; International Patent Application SerialNo. PCT/US2013/040058, entitled “Device, Method, and Graphical UserInterface for Displaying Additional Information in Response to a UserContact,” filed May 8, 2013; International Patent Application Serial No.PCT/US2013/040056, entitled “Device, Method, and Graphical UserInterface for Scrolling Nested Regions,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040054, entitled“Device, Method, and Graphical User Interface for Manipulating FramedGraphical Objects,” filed May 8, 2013; International Patent ApplicationSerial No. PCT/US2013/069489, entitled “Device, Method, and GraphicalUser Interface for Switching Between User Interfaces,” filed Nov. 11,2013; International Patent Application Serial No. PCT/US2013/069486,entitled “Device, Method, and Graphical User Interface for DeterminingWhether to Scroll or Select Content,” filed Nov. 11, 2013; InternationalPatent Application Serial No. PCT/US2013/069484, entitled “Device,Method, and Graphical User Interface for Moving a Cursor According to aChange in an Appearance of a Control Icon with SimulatedThree-Dimensional Characteristics,” filed Nov. 11, 2013; InternationalPatent Application Serial No. PCT/US2013/069483, entitled “Device,Method, and Graphical User Interface for Transitioning Between TouchInput to Display Output Relationships,” filed Nov. 11, 2013;International Patent Application Serial No. PCT/US2013/069479, entitled“Device, Method, and Graphical User Interface for Forgoing Generation ofTactile Output for a Multi-Contact Gesture,” filed Nov. 11, 2013;International Patent Application Serial No. PCT/US2013/069472, entitled“Device, Method, and Graphical User Interface for Navigating UserInterface Hierarchies,” filed Nov. 11, 2013; International PatentApplication Serial No. PCT/US2013/040108, entitled “Device, Method, andGraphical User Interface for Moving and Dropping a User InterfaceObject,” filed May 8, 2013; International Patent Application Serial No.PCT/US2013/040101, entitled “Device, Method, and Graphical UserInterface for Selecting User Interface Objects,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040098, entitled“Device, Method, and Graphical User Interface for Displaying ContentAssociated with a Corresponding Affordance,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040093, entitled“Device, Method, and Graphical User Interface for Transitioning BetweenDisplay States in Response to a Gesture,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040053, entitled“Device, Method, and Graphical User Interface for Selecting Objectwithin a Group of Objects,” filed May 8, 2013; U.S. Patent ApplicationSer. No. 61/778,211, entitled “Device, Method, and Graphical UserInterface for Facilitating User Interaction with Controls in a UserInterface,” filed Mar. 12, 2013; U.S. Patent Application Ser. No.61/778,191, entitled “Device, Method, and Graphical User Interface forDisplaying User Interface Objects Corresponding to an Application,”filed Mar. 12, 2013; U.S. Patent Application Ser. No. 61/778,171,entitled “Device, Method, and Graphical User Interface for DisplayingAdditional Information in Response to a User Contact,” filed Mar. 12,2013; U.S. Patent Application Ser. No. 61/778,179, entitled “Device,Method and Graphical User Interface for Scrolling Nested Regions,” filedMar. 12, 2013; U.S. Patent Application Ser. No. 61/778,156, entitled“Device, Method, and Graphical User Interface for Manipulating FramedGraphical Objects,” filed Mar. 12, 2013; U.S. Patent Application Ser.No. 61/778,125, entitled “Device, Method, And Graphical User Interfacefor Navigating User Interface Hierarchies,” filed Mar. 12, 2013; U.S.Patent Application Ser. No. 61/778,092, entitled “Device, Method, andGraphical User Interface for Selecting Object Within a Group ofObjects,” filed Mar. 12, 2013; U.S. Patent Application Ser. No.61/778,418, entitled “Device, Method, and Graphical User Interface forSwitching Between User Interfaces,” filed Mar. 13, 2013; U.S. PatentApplication Ser. No. 61/778,416, entitled “Device, Method, and GraphicalUser Interface for Determining Whether to Scroll or Select Content,”filed Mar. 13, 2013; U.S. Patent Application Ser. No. 61/747,278,entitled “Device, Method, and Graphical User Interface for ManipulatingUser Interface Objects with Visual and/or Haptic Feedback,” filed Dec.29, 2012; U.S. Patent Application Ser. No. 61/778,414, entitled “Device,Method, and Graphical User Interface for Moving and Dropping a UserInterface Object,” filed Mar. 13, 2013; U.S. Patent Application Ser. No.61/778,413, entitled “Device, Method, and Graphical User Interface forSelecting User Interface Objects,” filed Mar. 13, 2013; U.S. PatentApplication Ser. No. 61/778,412, entitled “Device, Method, and GraphicalUser Interface for Displaying Content Associated with a CorrespondingAffordance,” filed Mar. 13, 2013; U.S. Patent Application Ser. No.61/778,373, entitled “Device, Method, and Graphical User Interface forManaging Activation of a Control Based on Contact Intensity,” filed Mar.12, 2013; U.S. Patent Application Ser. No. 61/778,265, entitled “Device,Method, and Graphical User Interface for Transitioning Between DisplayStates in Response to a Gesture,” filed Mar. 12, 2013; U.S. PatentApplication Ser. No. 61/778,367, entitled “Device, Method, and GraphicalUser Interface for Moving a User Interface Object Based on an Intensityof a Press Input,” filed Mar. 12, 2013; U.S. Patent Application Ser. No.61/778,363, entitled “Device, Method, and Graphical User Interface forTransitioning Between Touch Input to Display Output Relationships,”filed Mar. 12, 2013; U.S. Patent Application Ser. No. 61/778,287,entitled “Device, Method, and Graphical User Interface for ProvidingFeedback for Changing Activation States of a User Interface Object,”filed Mar. 12, 2013; U.S. Patent Application Ser. No. 61/778,284,entitled “Device, Method, and Graphical User Interface for ProvidingTactile Feedback for Operations Performed in a User Interface,” filedMar. 12, 2013; U.S. Patent Application Ser. No. 61/778,239, entitled“Device, Method, and Graphical User Interface for Forgoing Generation ofTactile Output for a Multi-Contact Gesture,” filed Mar. 12, 2013; andU.S. Patent Application Ser. No. 61/688,227, entitled “Device, Method,and Graphical User Interface for Manipulating User Interface Objectswith Visual and/or Haptic Feedback,” filed May 9, 2012.

This application also relates to the following application: U.S. Utilityapplication Ser. No. 12/987,982, entitled “Intelligent AutomatedAssistant,” filed Jan. 10, 2011.

The content of these applications is hereby incorporated by reference inits entirety.

BACKGROUND 1. Field

The present disclosure relates generally to computer user interfaces,and more specifically to user interfaces and techniques for setting upan electronic device.

2. Description of Related Art

Modern electronic devices often have many customizable features that canbe set by a user according to the user's preferences. These features mayinclude the ability to perform various tasks or services which a usermay turn on or off based on personal preferences regarding privacy, datausage, battery life, or the like. Thus, there is an opportunity toprovide techniques and interfaces for allowing a user to set up andconfigure an electronic device. Modern electronic devices are alsocapable of communicating with other electronic devices via, for example,wireless communication. The ability to communicate with other devicesmay allow devices to share information and interact with each other.Thus, there is also an opportunity to provide techniques forestablishing communication between devices and to use the communicationto improve a setup process.

BRIEF SUMMARY

In some embodiments, a method comprises: at an electronic device with acamera, invoking a wireless communications pairing mode for pairing theelectronic device with an external device; obtaining an image via thecamera, the image containing a pattern displayed on a display screen ofthe external device, the pattern comprising identifying information ofthe external device; receiving data from the external device;determining whether the received data corresponds with the identifyinginformation; and in response to a determination that the received datacorresponds with the identifying information, registering the externaldevice as a paired device.

In some embodiments, an electronic device includes a camera unitconfigured to obtain images and a processing unit coupled to the cameraunit. The processing unit is configured to invoke a wirelesscommunications pairing mode for pairing the electronic device with anexternal device; enable obtaining of an image via the camera unit, theimage containing a pattern displayed on a display screen of the externaldevice, the pattern comprising identifying information of the externaldevice; and receive data from the external device. The processing unitis further configured to determine whether the received data correspondswith the identifying information; and, in response to a determinationthat the received data corresponds with the identifying information,register the external device as a paired device.

In some embodiments, a method comprises: at an electronic device with acamera, invoking a wireless communications pairing mode for pairing theelectronic device with an external device, wherein the pairing mode isinitially in a first state in which the electronic device will not pairwith the external device; obtaining an image via the camera, the imagecontaining a first pattern displayed on a display screen of the externaldevice; determining whether the first pattern corresponds with apredetermined pattern; in response to a determination that the firstpattern corresponds with the predetermined pattern, setting the pairingmode to a second state in which the electronic device will pair with theexternal device; receiving data from the external device; and inresponse to receiving the data from the external device, registering theexternal device as a paired device.

In some embodiments, an electronic device includes a camera unitconfigured to obtain images and a processing unit coupled to the cameraunit. The processing unit is configured to invoke a wirelesscommunications pairing mode for pairing the electronic device with anexternal device, wherein the pairing mode is initially in a first statein which the electronic device will not pair with the external device,and enable obtaining of an image via the camera unit, the imagecontaining a first pattern displayed on a display screen of the externaldevice. The processing unit is further configured to determine whetherthe first pattern corresponds with a predetermined pattern, and, inresponse to a determination that the first pattern corresponds with thepredetermined pattern, set the pairing mode to a second state in whichthe electronic device will pair with the external device. The processingunit is further configured to receive data from the external device and,in response to receiving the data from the external device, register theexternal device as a paired device.

In some embodiments, a method comprises: at an electronic device,invoking a wireless communications pairing mode for pairing theelectronic device with an external device; receiving data from theexternal device; detecting movement indicative of a physical contact atthe electronic device; and in response to receiving the data anddetecting the movement, registering the external device as a paireddevice.

In some embodiments, an electronic device includes a processing unitconfigured to invoke a wireless communications pairing mode for pairingthe electronic device with an external device, receive data from theexternal device, detect movement indicative of a physical contact at theelectronic device, and, in response to receiving the data and detectingthe movement, register the external device as a paired device.

In some embodiments, a method comprises: at an electronic device with atouch-sensitive display, displaying a configuration interface forconfiguring an orientation in which a wearable electronic device with anasymmetric geometry is to be worn; detecting a user selection of theorientation; and sending data representing the selected orientation tothe wearable electronic device, wherein: the selected orientationcorresponds to a display orientation of the wearable electronic device.

In some embodiments, an electronic device includes a touch-sensitivesurface unit configured to receive contacts, a display unit configuredto display a graphic user interface, and a processing unit coupled tothe display unit and the touch-sensitive surface unit. The processingunit is configured to enable display of a configuration interface forconfiguring an orientation in which a wearable electronic device with anasymmetric geometry is to be worn, detect a user selection of theorientation, and enable sending of data representing the selectedorientation to the wearable electronic device, wherein the selectedorientation corresponds to a display orientation of the wearableelectronic device.

In some embodiments, a method comprises: at an electronic device with adisplay, wherein the electronic device is configured to initiate adevice configuration sequence upon power-on of the electronic device,storing a personalized electronic message, wherein the electronicmessage is stored before an initial device configuration of theelectronic device; detecting a user instruction to power-on theelectronic device; determining whether the device configuration sequencehas previously been initiated or completed; in response to adetermination that the device configuration sequence has not previouslybeen initiated or completed, displaying the electronic message uponpower-on of the electronic device; and after displaying the electronicmessage: initiating the device configuration sequence; and displaying auser interface screen for device configuration.

In some embodiments, an electronic device configured to initiate adevice configuration sequence upon power-on of the electronic deviceincludes a display unit configured to display a graphic user interfaceand a processing unit coupled to the display unit. The processing unitis configured to store a personalized electronic message, wherein theelectronic message is stored before an initial device configuration ofthe electronic device, detect a user instruction to power-on theelectronic device, and determine whether the device configurationsequence has previously been initiated or completed. The processing unitis further configured to, in response to a determination that the deviceconfiguration sequence has not previously been initiated or completed,enable display of the electronic message upon power-on of the electronicdevice, and, after enabling display of the electronic message, initiatethe device configuration sequence, and enable display of a userinterface screen for device configuration.

In some embodiments, a method of initializing an electronic device usingan external device, the electronic device including a touch-sensitivedisplay, comprises: at the electronic device, displaying, on thetouch-sensitive display, at least one device initialization screen;after displaying the at least one device initialization screen,displaying an instruction screen instructing a user to pair the externaldevice with the electronic device; sending first data via wirelesscommunication; displaying, on the touch-sensitive display, a patterncomprising identifying information of the electronic device; receivingsecond data indicating that the external device and the electronicdevice have been paired using the first data; and after receiving thesecond data, providing an aural or haptic indication that the electronicdevice and the external device have been paired.

In some embodiments, an electronic device configured to be initializedusing an external device includes a touch-sensitive surface unitconfigured to receive contacts, a display unit configured to display agraphic user interface, and a processing unit coupled to thetouch-sensitive surface unit and the display unit. The processing unitis configured to enable display of at least one device initializationscreen, and, after enabling display of the at least one deviceinitialization screen, enable display of an instruction screeninstructing a user to pair the external device with the electronicdevice. The processing unit is further configured to enable sending offirst data via wireless communication, enable display of a patterncomprising identifying information of the electronic device, receivesecond data indicating that the external device and the electronicdevice have been paired using the first data, and, after receiving thesecond data, enable an aural or haptic indication that the electronicdevice and the external device have been paired.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having atouch-sensitive display in accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIGS. 4A and 4B illustrate an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 5A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display and a rotatable input mechanism inaccordance with some embodiments.

FIG. 5B illustrates a portable multifunction device having atouch-sensitive display and a rotatable input mechanism in accordancewith some embodiments.

FIGS. 6A-6C illustrate exemplary user interface screens.

FIGS. 7A-7B illustrate exemplary user interface screens.

FIGS. 8A-8B illustrate exemplary user interface screens.

FIG. 9 illustrates an exemplary user interface screen.

FIGS. 10A-10B illustrate exemplary user interface screens.

FIGS. 11A-11B illustrate exemplary user interface screens.

FIGS. 12A-12B illustrate exemplary user interface screens.

FIGS. 13A-13B illustrate exemplary user interface screens.

FIGS. 14A-14C illustrate exemplary user interface screens.

FIG. 15 is a flow diagram illustrating a process for pairing anelectronic device with an external device.

FIG. 16 is a flow diagram illustrating a process for pairing anelectronic device with an external device.

FIG. 17 is a flow diagram illustrating a process for pairing anelectronic device with an external device.

FIG. 18 is a flow diagram illustrating a process for configuring anorientation in which a wearable electronic device with an asymmetricgeometry is to be worn is displayed.

FIG. 19 is a flow diagram illustrating a process for displaying apersonalized message on the display of an electronic device.

FIG. 20 is a flow diagram illustrating a process for setting up anelectronic device.

FIG. 21 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 22 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 23 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 24 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 25 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 26 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 27 is a functional block diagram of an electronic device inaccordance with some embodiments.

DETAILED DESCRIPTION

In the following description of the disclosure and embodiments,reference is made to the accompanying drawings in which it is shown byway of illustration specific embodiments that can be practiced. It is tobe understood that other embodiments and examples can be practiced andchanges can be made without departing from the scope of the disclosure.

There is a need to set up a personal electronic device upon booting upthe device for the first time or upon resetting the device. Setting upthe device may include, among other things, initializing systems andprograms that run on the device and configuring the device. An initialdevice configuration sequence may include installing software, settingdevice parameters, receiving and storing information (e.g., contactinformation of user contacts), etc. An initial device configurationsequence may also allow a user to set and/or change configurationparameters of the device according to his or her personal preferences.Boot up is a desirable time to prompt a user to set parameters that arecritical to operating the device or that the user may not haveintuitively known were configurable. For example, the device may displaya sequence of user interface screens to guide the user through aninitial device configuration sequence in which the user may set certainconfiguration parameters. The initial configuration sequence should besimple, clear, quick, efficient, and intuitive.

Setup may also include pairing the electronic device with an external orcompanion device. As used here, pairing two electronic devices includesestablishing a means of communication between the two devices. The meansof communication may include those described in U.S. Patent ApplicationSer. No. 62/005,751, “Predefined Wireless Pairing,” filed May 30, 2014,which is incorporated in this disclosure by reference. Once the devicesare paired, they may exchange data including data that may be usedduring initial device configuration. Pairing may also allow a device tobe configured using a user interface provided by the other paireddevice. For example, recent advances in computer technology have enabledmanufacturers to produce powerful computing devices in relatively smallform factors. However, small devices may be unable to provide a userinterface large enough to be suitable for user configuration. Instead,the device being configured may be paired with an external device with alarger user interface that provides the ability to set parameters on thedevice being configured. Such techniques can reduce the time and effortrequired to begin using the device and can make the device more usefulto the user.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B illustrate exemplary devicesupon which the techniques described herein for setting up an electronicdevice may be applied. FIGS. 6A-6C, 7A-7B, 8A-8B, 9, 10A-10B, 11A-11B,12A-12B, 13A-13B, and 14A-14C depict exemplary user interfaces forsetting up an electronic device. The user interfaces in the figures areused to illustrate the processes described below, including theprocesses in FIGS. 15-20.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 may include one or more computer-readable storage mediums.The computer-readable storage mediums may be tangible andnon-transitory. Memory 102 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 122 may control access tomemory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 and convertthe detected contact into interaction with user-interface objects (e.g.,one or more soft keys, icons, web pages, or images) that are displayedon touch screen 112. In an exemplary embodiment, a point of contactbetween touch screen 112 and the user corresponds to a finger of theuser.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conferencing module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 may be used to manage an address book orcontact list (e.g., stored in application internal state 192 of contactsmodule 137 in memory 102 or memory 370), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 137, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation, and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions, data on stores and otherpoints of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 152, FIG. 1A). In some embodiments, memory 102may store a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules may be combined or otherwise rearranged invarious embodiments. In some embodiments, memory 370 may store a subsetof the modules and data structures identified above. Furthermore, memory370 may store additional modules and data structures not describedabove.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 may optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface) may haveone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data thatrepresents the intensity of touches. The user interface of device 500can respond to touches based on their intensity, meaning that touches ofdifferent intensities can invoke different user interface operations ondevice 500.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013 and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 may be a rotatable input device or a depressible androtatable input device, for example. Input mechanism 508 may be abutton, in some examples.

Input mechanism 508 may be a microphone, in some examples. Personalelectronic device 500 can include various sensors, such as GPS sensor532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, and/or a combination thereof, all ofwhich can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 1500-2000 (FIGS. 15-20).The computer-executable instructions can also be stored and/ortransported within any non-transitory computer-readable storage mediumfor use by or in connection with an instruction execution system,apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. For purposes of this document, a“non-transitory computer-readable storage medium” can be any medium thatcan tangibly contain or store computer-executable instructions for useby or in connection with the instruction execution system, apparatus, ordevice. The non-transitory computer-readable storage medium can include,but is not limited to, magnetic, optical, and/or semiconductor storages.Examples of such storage include magnetic disks, optical discs based onCD, DVD, or Blu-ray technologies, as well as persistent solid-statememory such as flash, solid-state drives, and the like. Personalelectronic device 500 is not limited to the components and configurationof FIG. 5B, but can include other or additional components in multipleconfigurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example,an image (e.g., icon), a button, and text (e.g., hyperlink) may eachconstitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of: an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms eliminatenarrow spikes or dips in the intensities of the swipe contact forpurposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

Attention is now directed towards embodiments of user interfaces andassociated processes that may be implemented on a multifunction devicewith a display and a touch-sensitive surface, such as devices 100, 300,and/or 500 (FIGS. 1A, 3A, and/or 5A), to improve a user's experience insetting up the device. For brevity, the functionalities described hereinmay be referred to as “setup” functionalities.

User interfaces for configuring an electronic device are illustrated byexemplary screens that one or more devices 100, 300, and/or 500 candisplay as part of a device setup process.

1. Initialization

FIGS. 6A-6C demonstrate exemplary initialization screens for anelectronic device. FIG. 6A shows an exemplary electronic device 600. Insome embodiments, device 600 may be one or more of devices 100 (FIG. 1),300 (FIG. 3), and/or 500 (FIG. 5). For purposes of illustration, device600 is a personal electronic device with a touch-sensitive display, suchas personal electronic device 500. In the embodiment illustrated in FIG.6A, personal electronic device 600 includes a rotatable input mechanism601 on one of its sides, which may give an asymmetric physical geometryto device 600.

In FIG. 6A, an exemplary boot-up screen 602 is displayed on device 600.Boot-up screen 602 may be displayed in response to an instruction topower-on or restart device 600. The command may be a software command ora user input via hardware, such as a button press or a touch on a userinterface object displayed on the touch-sensitive display. Boot-upscreen 602 may be displayed during at least some portion of a boot-upprocess. The boot-up process may include operations such as performing apower-on self-test, locating and initializing peripheral devices,loading and starting an operating system or other software, or the like.Boot-up screen 602 may show any desired text, image, icon, animation,video, or the like. In FIG. 6A, boot-up screen 602 shows an icon 604 inthe shape of a star.

FIG. 6B shows an exemplary welcome screen 606 that device 600 candisplay on its display. Device 600 may transition from displayingboot-up screen 602 to displaying welcome screen 606 after at least aportion of the boot-up process has completed. Welcome screen 606 mayinclude a welcome message containing any desired text, image, icon,animation, video, or the like. In FIG. 6B, welcome screen 606 showswelcome message 608, which includes text that identifies device 600.

Welcome screen 606 may also include an affordance 610 showing the text“NEXT”. As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of device 600 as well as devices 100, 300, and/or 500 (FIGS. 1,3, and 5). For example, an image (e.g., icon), a button, and text (e.g.,hyperlink) may each constitute an affordance. In some embodiments, auser may select an affordance via a mouse gesture (e.g., hover, click,double-click, drag). In some embodiments, a user may select anaffordance via a touch-based gesture (e.g., tap, swipe, flick, longtouch).

In the example of FIG. 6B, a user may select the displayed affordance610 to instruct device 600 to continue to the next step or screen in theinitialization process. For example, in response to a tap gesture onaffordance 610, electronic device 600 may continue the initializationprocess. Alternatively, a user may cause the electronic device 600 totransition to the next screen or continue the initialization process bya swipe gesture from right to left on the touch-sensitive display orusing the rotatable input mechanism 601.

In one embodiment, electronic device 600 continues the initializationprocess by transitioning the display to an optional personalized messagescreen. A personalized message screen may include a personalized messagecontaining any desired text, image, icon, animation, video, or the likeand may have been received and loaded onto the device prior to shipping.FIG. 6C shows an exemplary personalized message screen 612 that includesa personalized message 614 with text 616 that says “HAPPY BIRTHDAY!LOVE, MOM” and an icon 618 showing a child with a party hat, present,and balloon.

Personalized message screen 612 also includes affordances 620 and 622.Affordance 620 has an icon including the text “NEXT”. A user may selectaffordance 620 to instruct device 600 to continue to the next step orscreen in the initialization process. That is, in response to a tapgesture on affordance 620, electronic device 600 continues theinitialization process. Affordance 622 includes an icon of an arrow headpointing to the left. A user may select affordance 622 to cause device600 to display the previous screen. That is, in response to a tapgesture on affordance 622, electronic device 600 returns to a previousstep or displays a screen displayed prior to screen 612.

In one embodiment, the personalized message 614 is created or chosen bya user and is received and loaded onto device 600 before device 600 isinitially configured. The personalized message 614 may be personalizedfor an intended user of the electronic device 600. For example, themessage 614 shown in FIG. 6C may be chosen by a mother who intends togive the device 600 to her child as a birthday present. The personalizedmessage 614 may be obtained at the point-of-sale of device 600. Forexample, the personalized message 614 may be input into a point-of-saledevice (e.g., a computer, server, etc.) that sends the personalizedmessage 614 to device 600. Device 600 may receive the personalizedmessage 614 and store it in local memory prior to being configured forthe first time (i.e., before an initial device configuration).

Upon detecting an instruction to power-on device 600 (e.g., via a userinput or software command), device 600 may determine whether a deviceconfiguration sequence has previously been initiated or completed. Inresponse to determining that the device configuration sequence has notpreviously been initiated or that the device configuration sequence wasinitiated but not completed, the electronic device may display apersonalized message screen 612 with the personalized message 614 beforeinitiating the device configuration sequence or during the deviceconfiguration sequence. Alternatively, in response to determining thatthe device configuration sequence has previously been initiated andcompleted, the electronic device may bypass display of the personalizedmessage screen and display the next scheduled screen.

In some embodiments, the personalized electronic message 614 is notdisplayed again after an initial device configuration has beencompleted. However, the electronic device 600 may also be capable ofbeing reset so that it returns to a state in which it is as thoughdevice 600 has never been configured (e.g., the device configurationsequence has not previously been initiated or completed). In this case,the personalized electronic message 614 may be displayed again uponpower-on after having been reset.

Turning now to FIG. 7A, an exemplary instruction screen 700 that device600 can display on its display is described. The instruction screen 700may include an image, icon, animation, video, text, or the like thatprompts the user to take an action. For example, instruction screen 700includes text 702 instructing the user to position the device. In oneembodiment, a user may be instructed to attach the electronic device 600to a body part such as one of the user's wrist.

Instruction screen 700 also includes affordances 704 and 706. Affordance704 has an icon including the text “NEXT”. Selecting affordance 704 mayinstruct device 600 to continue to the next step or screen. That is, inresponse to a tap gesture on affordance 704, electronic device 600continues the setup process. A user may select affordance 704 toindicate that the user has complied or intends to comply with theinstruction 702. In an alternate embodiment, the device detects, usingone or more biometric sensors, that the user has positioned the deviceand advances to screen 710 without the need for user contactingaffordance 704. Affordance 706 includes an icon of an arrow headpointing to the left. A user may select affordance 706 to cause device600 to display the previous screen. That is, in response to a tapgesture on affordance 706, electronic device 600 returns to a previousstep or displays a screen displayed prior to screen 700.

FIG. 7B shows another exemplary instruction screen 710 that device 600can display on its display. Instruction screen 710 may be displayed toprompt a user to take an action that will initiate pairing of theelectronic device 600 with an external electronic device, such as theuser's phone. In some embodiments, the external device may be one ormore of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5). For thepurpose of illustration in the examples and descriptions that follow,the external device is described with reference to phone 850 shown inFIG. 8B (e.g., an iPhone®) discussed in greater detail below.

The external device may operate in a pairing mode that allows it to pairwith another device, such as device 600. As used herein, pairing moderefers to an operating mode in which two devices attempt to register oneanother for future wireless communications. For example, the process ofinitially connecting two Bluetooth-enabled devices involves enteringinto pairing mode on the devices.

In some embodiments, wireless communication, for purposes of pairing,occurs over a peer-to-peer wireless communication protocol such asBluetooth and/or Bluetooth Low Energy (BTLE). In some embodiments,wireless communication for purposes of pairing functionality utilizesmore than one wireless communication protocol. For example, WiFi may beused in addition to BTLE. In these embodiments, an initial communicationbetween two devices may occur over a lower powered protocol, such asBTLE, even if the protocol yields a slower data transfer speed.Subsequent communications may occur over a secondary network that isrelatively faster, such as WiFi.

The pairing mode of the external device may be invoked by running asoftware program. The software program may be part of an operatingsystem or an application program. In one embodiment, the external devicedisplays an affordance (e.g., a selectable icon) representing anapplication for pairing the external device with another device (e.g.,device 600). Selecting the application affordance may launch theapplication and invoke the pairing mode.

In some embodiments, the application affordance is displayed on theexternal device only when device 600 is within communication range ofthe external device. For example, device 600 may wirelessly transmitdata that represents a request to pair or that indicates it is capableof pairing with another device. If the external device is not withincommunication range, the affordance is not displayed. However, if theexternal device receives the data, and therefore is within communicationrange of device 600, then the application affordance is displayed.

In another embodiment, when the external device is not within range, theapplication affordance is displayed but in a manner which indicates thatthe application cannot be launched. For example, the applicationaffordance may appear greyed-out or semi-transparent to indicate thatthe application cannot be launched. When the external device comeswithin communication range of device 600, the visual appearance of theapplication affordance may be changed to indicate that the applicationcan be invoked.

In some embodiments, the external device may include a setting thatallows a user to turn on or off a range-dependent display feature of theapplication affordance. That is, the user may determine whether or notthe display and/or appearance of the application affordance shoulddepend on whether the external device is within range of a device withwhich it can pair.

Returning to FIG. 7B, instruction screen 710 includes text 712instructing the user to launch an application on the user's phone topair the device 600. In one embodiment, the application is launched byexecuting a tap gesture on an affordance associated with the applicationdisplayed on the user's phone. The application may invoke a wirelesscommunications pairing mode for pairing the device 600 with the user'sphone.

Instruction screen 710 also includes affordances 714 and 716. Affordance714 has an icon including the text “NEXT”. Selecting affordance 714 mayinstruct device 600 to continue to the next step or screen. That is, inresponse to a tap gesture on affordance 714, electronic device 600continues the setup process. Accordingly, a user may select affordance714 to indicate that the user has complied or intends to comply with theinstruction 712. That is, selecting affordance 714 may indicate that theuser has or intends to launch an application program for pairing thephone with the electronic device. Affordance 716 includes an icon of anarrow head pointing to the left. A user may select affordance 716 tocause device 600 to display the previous screen. That is, in response toa tap gesture on affordance 716, electronic device 600 returns to aprevious step or displays a screen displayed prior to screen 710.

2. Pairing

FIG. 8A shows another exemplary instruction screen 800 that device 600can display on its display. Instruction screen 800 may be displayedafter screen 710 to facilitate pairing the device 600 with an externaldevice 850. Instruction screen 800 includes text 802 instructing theuser to take a picture of instruction screen 800 with a camera on theuser's phone to pair the electronic device 600 with the user's phone.

Instruction screen 800 also includes an image containing a pattern 804.The displayed image may include wavelengths that are visible to thehuman eye. Alternatively, the image may only include wavelengths thatare invisible to the human eye, but which can be produced by the displayon device 600 and detected by the camera of phone 850. In oneembodiment, the instruction screen 800 may display an invisible imagecontaining the pattern 804 along with a visible image. The visible imagemay be aesthetically appealing to the user, while the invisible imagemay be less appealing but contains more information and/or is easier torecognize and/or process by a processor facilitating the pairing.

The pattern 804 may be used to identify or authenticate the device 600.In one embodiment, the pattern comprises identifying information of thedevice 600. Identifying information may include any design, symbol,pattern, sequence, indication, or the like that identifies the device600, such as a quick response code or a bar code. The identifyinginformation may be unique to device 600 or may generally indicate thetype of device (e.g., iPhone®, wearable electronic device, etc.).

FIG. 8B shows exemplary external device 850 that may be paired withdevice 600. In FIG. 8B, external device 850 is a phone with a camerathat may be used to take a picture of device 600 while instructionscreen 800 is displayed. Using the camera of external device 850, a usermay obtain an image containing a visual representation of the device 600including the pattern 804 displayed on the screen of electronic device600. FIG. 8B shows external device 850 displaying an example of anobtained image 852 of electronic device 600. Image 852 shows electronicdevice 600 displaying instruction screen 800 with the pattern 804.

External device 850 may process the obtained image 852 to extract theidentifying information contained in the pattern 804. External device850 may then use the extracted identifying information to authenticatethe device 600 for pairing. In one embodiment, the electronic device 600transmits data via wireless communication. The data may includeinformation identifying the electronic device 600. The data may alsoinclude information representative of the pattern displayed on screen800. Electronic device 600 may send the data in response to anindication that the user has launched or intends to launch anapplication program for pairing the user's phone with device 600 (e.g.,selecting affordance 714 on screen 700 as described above).

The external device 850 may receive the data transmitted by electronicdevice 600 and determine whether the identifying information in thereceived data corresponds with the identifying information in the imageof the pattern obtained by the camera. If the external device 850determines that the received data corresponds with the identifyinginformation in pattern 804, then the external device 850 may registerdevice 600 as a paired device. Alternatively, if the external device 850determines that the received data does not correspond with theidentifying information in pattern 804, then the external device 850 maynot register device 600 as a paired device and/or may continue toreceive data.

Registering device 600 as a paired device may be done in various ways.In one embodiment, in response to determining that the received datacorresponds with the identifying information, the external device 850may transmit, e.g., via wireless communication, data representing arequest to pair with the device 600. In another embodiment, device 600may transmit data representing a request to pair with an externaldevice. External device 850 may receive the data and accept the requestto pair after authenticating device 600 as described above.

As mentioned above, the data transmitted by device 600 may include dataindicative of the pattern 804. If so, the external device 850 maycompare the data indicative of the pattern against the pattern 804 indetermining whether the received data corresponds with the identifyinginformation.

In another embodiment, the pairing mode of external device 850 mayinitially be in a first state in which the external device 850 will notpair with the electronic device 600 without further input or action. Toswitch to a state in which the external device 850 will pair, externaldevice 850 may process picture 852 and determine whether pattern 804corresponds with at least one pattern in a set of predeterminedpatterns. The set of predetermined patterns may include one or morepatterns that can be recognized by the external device 850 and cause theexternal device 850 to operate in a state in which it will pair withanother device. The set of predetermined patterns may be included with aprogram that facilitates pairing, downloaded from the Internet, orobtained by some other means. In response to a determination that thepattern 804 corresponds with one or more predetermined patterns, thepairing mode is set to a second state in which the external device 850will pair with another electronic device. Alternatively, in response toa determination that the pattern 804 does not correspond with one ormore predetermined patterns, the pairing mode may be kept in the firststate.

In one embodiment, while in the second state, the external device 850may wirelessly transmit a request to pair and attempt to pair with anydevice that accepts the request to pair. In another embodiment, while inthe second state, the external device 850 may receive a request to pairfrom device 600, accept the received request, and attempt to pair withthe requesting device (i.e., device 600). That is, while the pairingmode is set to the second state, the external device 850 may receive thedata transmitted by the device 600 and, in response to receiving thedata from device 600, register the device 600 as a paired device.

Returning to FIG. 8A, instruction screen 800 does not include “BACK”(e.g., a left-pointing arrow) or “NEXT” affordances. In one embodiment,device 600 may transition from screen 800 to a next screen uponreceiving an indication that it is paired with external device 850.Alternatively, instruction screen 800 may include affordances analogousto affordances 714 and 716 described above that provide the ability toreturn to a previous screen or process or advance to a subsequent screenor process.

Although pairing as described above relies on a displayed pattern (e.g.,pattern 804), there are various alternative methods for pairing twodevices. In one embodiment, device 600 may be paired with the externaldevice 850 by tapping the external device 850 with the device 600, orvice versa. The external device 850 may include sensors such as thosedescribed above (e.g., accelerometers, gyroscopes, etc.) to detectmovement indicating that the external device 850 has been tapped. In oneembodiment, tapping the external device 850 causes it to be set in astate in which it will pair with another device.

FIG. 9 shows an exemplary instruction screen 900 that device 600 candisplay on its display. Instruction screen 900 includes text 902instructing the user to tap the user's phone with the electronic device600 to pair the two devices. While in a pairing mode, the externaldevice 850 may detect movement indicative of a physical contact. Theexternal device 850 may also receive data transmitted by device 600 thatincludes identifying information of device 600. In response to receivingthe data transmitted by the device 600 and detecting the movement, theexternal device 850 may register device 600 as a paired device.

Although not shown, instruction screen 900 may include affordancesanalogous to affordances 714 and 716 described above that provide theability to return to a previous screen or process or advance to asubsequent screen or process.

Once the device 600 has paired with the external device 850, the device600 and/or the external device 850 may provide an indication that thedevices have paired. The indication may include an aural indication,such as a chime, ping, beep, tune, or the like. The indication may also,or alternatively, include a haptic indication, such as tactile feedbackin the form of buzzing, vibrating, or pulsing. In one embodiment, eachdevice provides an indication simultaneously with the other. In anotherembodiment, the devices provide indications one after the other in aback-and-forth manner which indicates that the two devices are in sync.

The device 600 and/or the external device 850 may also provide a visibleindication that pairing has occurred. FIG. 10A shows a screen 1000 thatmay be displayed at device 600 to indicate that the device 600 isconnecting to the external device 850. Screen 1000 includes text 1002and icon 1004 which indicate that device 600 is connecting to theexternal device 850. Icon 1004 may be a static image or it may beanimated to indicate that connection is in progress.

FIG. 10B shows a screen 1010 that may be displayed at external device850 to indicate that the external device 850 is connecting to the device600. Screen 1010 includes text 1012 and icon 1014, which indicate thatthe phone 850 is connecting to electronic device 600. Icon 1014 may be astatic image or it may be animated to indicate that connection is inprogress.

As mentioned above, pairing may create a communication link between theelectronic device 600 the external device 850. Once the two devices areconnected, data may be transferred wirelessly between the two devicesover the communication link. In one embodiment, after registering thedevice 600 as a paired device, the external device 850 may send userinformation to the device 600. The external device 850 may access userinformation from local storage or from a remote source (e.g., a webserver) via, for example, a WiFi connection. User information mayinclude WiFi settings, contact information of a user's contacts,information identifying one or more applications installed on theexternal device 850, notification settings, identification informationabout the user or the external device 850, default device settings(e.g., language, font size, etc.), or the like.

User information may also include service settings. Exemplary servicesmay provide the capability to connect wirelessly to the Internet or todetermine the location of the phone. Other services may providediagnostic capabilities or an Intelligent Automated Assistant asdescribed in U.S. Utility application Ser. No. 12/987,982, entitled“Intelligent Automated Assistant,” filed Jan. 10, 2011.

In one embodiment, the transfer of user information must be completebefore proceeding to the next step in the setup process. Alternatively,transfer of user information may continue in parallel with subsequentsteps of the setup process.

3. Configuration

Setting up an electronic device may also include a configurationsequence in which various device parameters are set and/or confirmed. Aconfiguration sequence may include, among other things, setting and/orconfirming a face image to be displayed on the electronic device and/orthe status of service agreements.

If the device is wearable, configuration may also include setting and/orconfirming the orientation in which the device is to be worn. In oneembodiment, the device 600 is a wearable electronic device, such as awatch intended to be worn on a user's wrist.

FIG. 11A shows an exemplary configuration status screen 1100 that may bedisplayed on the display of electronic device 600. Configuration statusscreen 1100 includes text 1102 indicating that the screen shows thestatus of an orientation parameter. The orientation parameter mayrepresent the orientation in which device 600 is intended to be worn bythe user. The orientation may include a wrist orientation and arotatable input mechanism orientation. The status of both the wristorientation and the rotatable input mechanism orientation may be either“RIGHT” or “LEFT”. Text 1104 shows that the wrist orientation status is“LEFT”, which indicates that device 600 is to be worn on the user's leftwrist. Text 1106 shows that the rotatable input mechanism orientationstatus is “RIGHT”, which indicates that the device is to be worn suchthat the rotatable input mechanism 601 is on the right from a frontperspective facing the display. As shown in FIG. 11A, device 600 isoriented in the RIGHT rotatable input mechanism orientation.

In one embodiment, the orientation of the device 600 may determine thedirection in which information is displayed on the screen. That is, theorientation may correspond to a display orientation of the device. Forexample, if the device 600 is intended to be worn on a user's left wristwith the rotatable input mechanism 601 on the right, the display shouldbe oriented such that the right side of a displayed screen is on thesame side as the rotatable input mechanism 601. However, if the device600 is oriented such that the rotatable input mechanism 601 is on theleft, the screen should be displayed so that the right side of thescreen is displayed on the side opposite the rotatable input mechanism601. Accordingly, a first orientation (e.g., rotatable input mechanismorientation LEFT) may correspond to a first display orientation of awearable electronic device, and a second orientation (e.g., rotatableinput mechanism orientation RIGHT) may correspond to a second displayorientation. In the example provided above, the second displayorientation is rotated 180 degrees relative to the first displayorientation.

The orientation of the device 600 may also determine the response torotation of the rotatable input mechanism 601. In one embodiment,setting the rotatable input mechanism orientation to “RIGHT” causesdevice 600 to perform a scroll-up operation on displayed information inresponse to a clockwise rotation of the rotatable input mechanism 601and a scroll-down operation in response to a counter-clockwise rotation.When the rotatable input mechanism orientation is set to “LEFT”,electronic device 600 performs a scroll-up operation in response to acounter-clockwise rotation of the rotatable input mechanism 601 and ascroll-down operation in response to a clockwise rotation.Alternatively, an orientation of “RIGHT” may cause the device toscroll-up in response to a counter-clockwise rotation, and anorientation of “LEFT” may cause the device to scroll-up in response to aclockwise rotation.

Turning now to FIG. 11B, an exemplary configuration interface screen1110 that may be displayed on the display of external device 850 isdescribed. In some embodiments, device 600 may have a relatively smalldisplay screen, which may make it difficult to set configurationparameters on device 600. Instead, a user may wish to find, select,and/or confirm desired configuration settings on a screen of an externaldevice having a relatively larger display, such as screen 1110 onexternal device 850.

Configuration interface screen 1110 includes text 1112 prompting theuser to select an orientation in which the user intends to wear theelectronic device 600. Configuration interface screen also includesaffordances 1114, 1115, 1116, and 1117, which allow a user to select adesired wrist orientation and rotatable input mechanism orientation.

In one embodiment, device 600 may send data to external device 850 toinform it of the current orientation status. This may allow theaffordances associated with the current orientation status to behighlighted. For example, affordances 1114 and 1117 may be highlightedto indicate that the wrist orientation of electronic device 600 is setto “LEFT” and the rotatable input mechanism orientation is set to“RIGHT”, as shown in FIG. 11A.

A user may change the orientation status of device 600 using externaldevice 850 by selecting one of the affordances associated with adifferent orientation. For example, a user may select affordance 1115 tochange the wrist orientation from “LEFT” to “RIGHT”. In response toselection of an affordance associated with a different orientation,external device 850 may send data representing the selected orientationstatus to electronic device 600. In response to receiving the selectedorientation status, device 600 may set the orientation to the selectedvalue. Furthermore, external device 850 may update screen 1110 tohighlight the affordance associated with the newly selected orientation.

In another embodiment, the device 600 may be configured to determine howthe device is being worn based on the motion and position of the device.The device 600 may include sensors to detect that it is being worn andto track the motion and position (e.g., spatial orientation) of thedevice. Device 600 may then determine the wrist and rotatable inputmechanism orientations based on the detected motion and position. Forexample, motion from left to right while the device 600 is being raisedmay indicate that the device is being worn on the user's left wrist.

In another embodiment, external device 850 may determine the orientationof device 600 based on an image of device 600. For example, image 852described above with respect to pairing device 600 with external device850 may include a representation of device 600 positioned on the user.External device 850 may process image 852 to determine the orientationof device 600 based on the position of the rotatable input mechanism601, angle of the display and/or text, features of the user's armincluded in the image, and/or other features or indications oforientation that may be extracted from image 852. In response todetermining the orientation of device 600, external device 850 may senddata to device 600 representing the determined orientation. Device 600may then set the orientation status in response to receiving the data.

Turning now to FIG. 12A, an exemplary configuration interface screen1200 that may be displayed on the display of device 600 to set orconfirm the status of services available to the device 600 is described.Configuration interface screen 1200 includes text 1201, 1203, and 1205identifying three services available to the electronic device 600(SERVICE 1, SERVICE 2, and SERVICE 3, respectively). Services mayinclude the functionalities or capabilities described above. The statusof a service (e.g., ON or OFF) may represent an agreement by a user toallow the service to operate on the device 600 or for a third party toprovide the service. Configuration interface screen 1200 also includesaffordances 1202, 1204, and 1206, each corresponding to one of the threeservices (SERVICE 1, SERVICE 2, and SERVICE 3, respectively). Theaffordances indicate the current status of the corresponding service andcan be selected to change the status of the service. In FIG. 12A, theaffordances may be tapped or swiped to change the status of the servicesbetween ON and OFF. The appearance of the affordances may be updated toindicate a change in status. Configuration interface screen 1200 alsoincludes affordances analogous to affordances 714 and 716 describedabove that provide the ability to return to a previous screen or processor advance to a subsequent screen or process.

FIG. 12B shows an exemplary configuration interface screen 1210 that maybe displayed on the display of external device 850. Configurationinterface screen 1210 includes text 1211, 1213, and 1215 identifyingthree services available to the electronic device 600 (SERVICE 1,SERVICE 2, and SERVICE 3, respectively). Configuration interface screen1210 also includes affordances 1212, 1214, and 1216 each correspondingto one of the three services (SERVICE 1, SERVICE 2, and SERVICE 3,respectively). The affordances indicate the current status of thecorresponding service and can be selected to change the status of theservice on device 600. The affordances may be tapped or swiped to changethe status of the services between ON and OFF. The appearance of theaffordances may be updated to indicate a change in status. In responseto selection of an affordance that changes the status of a service,external device 850 may send data representing the selected servicestatus to device 600. In response to receiving the selected status,electronic device 600 may set the service status to the selected value.Furthermore, external device 850 may update screen 1210 to indicate thenewly selected status. External device 850 may also update screen 1210to indicate changes in status caused by a selection at device 600.

FIG. 13A shows another exemplary configuration interface screen 1300that may be displayed on the display of device 600. Configurationinterface screen 1300 includes an icon 1302 of an image that is to beused as a face for the display of the device 600. In one embodiment,device 600 is a watch and icon 1302 represents a clock face. Theselected face may be displayed while in a default state or a clock mode.In one embodiment, a user may select a different face with a swipegesture on the touch-sensitive display. For example, in response to aswipe from right to left, the electronic device may change the selectedface to a different face and display the different face.

FIG. 13B shows an exemplary configuration interface screen 1310 that maybe displayed on the display of phone 850. Configuration interface screen1310 includes affordances 1311-1316 each corresponding to a differentpotential face for device 600. Screen 1310 may indicate the currentlyselected face by highlighting the corresponding affordance. In FIG. 13B,affordance 1312 is highlighted by circle 1318 to indicate that the staricon is the currently selected face, as shown in FIG. 13A.

The affordances can be selected to change the status of the face ondevice 600. In response to selection of an affordance corresponding to aparticular face, external device 850 may highlight the selectedaffordance and send data representing the selected face to device 600.In response to receiving the data representing the selected face, device600 may set the face to the selected face.

Returning to FIG. 13A, configuration interface screen 1300 also includesaffordances 1304 and 1306. Affordance 1304 is analogous to affordance716 described above and provides the ability to return to a previousscreen or process. Affordance 1306 includes the text “DONE”. In oneembodiment, screen 1300 may be the last screen displayed by device 600in a device configuration sequence or a setup process. The text “DONE”may indicate to the user that selecting a face is the last step of setupor configuration. A user may select affordance 1306 to indicate that thecurrently displayed face is the one the user wants and that the user isdone with setup. In response to a user selection of affordance 1306,electronic device 600 may set the status of the initial configurationsequence as complete and transition the display to a notificationscreen, such as screen 1400 discussed below with reference to FIG. 14A.Alternatively, the display on device 600 may transition from screen 1300to a home screen, such as screen 1410 discussed below with reference toFIG. 14B. Furthermore, in response to a user selection of affordance1306, device 600 may send data to paired external device 850 indicatingthat the initial configuration sequence is complete. In response toreceiving the data, external device 850 may transition its display to ahome screen or, alternatively, a notification screen such as screen 1420discussed below with reference to FIG. 14C.

FIG. 14A shows an exemplary notification screen 1400 that may bedisplayed on the display of device 600. Notification screen 1400 mayinclude an indication that an initial device configuration sequence iscomplete. In FIG. 14A, screen 1400 includes text 1402, which indicatesto the user that initial configuration is done. Notification screen 1400also includes affordances 1404, which provides the ability to return toa previous screen or step. In one embodiment, device 600 automaticallytransitions to the home screen 1410 (discussed below) after notificationscreen 1400 has been displayed for a predetermined amount of time.

FIG. 14B shows an exemplary home screen 1410 that may be displayed onthe display of device 600. Home screen 1410 may be displayed followingcompletion of an initial configuration sequence. Home screen 1410 mayinclude one or more affordances 1412. When affordance 1412 is selected,device 600 may launch a corresponding application. Home screen 1410 mayalso include a user interface object 1414 that displays the currenttime. In one embodiment, user interface object 1414 includes the faceselected during the initial configuration sequence.

FIG. 14C shows an exemplary notification screen 1420 that may bedisplayed on the display of paired external device 850. In oneembodiment, screen 1420 may be displayed in response to a notificationfrom device 600 that the initial configuration sequence is complete. InFIG. 14C, text 1422 is displayed to indicate that the initialconfiguration sequence is complete. Notification screen 1420 may alsoallow for additional setup of device 600 that was not part of theinitial configuration sequence. Notification screen 1420 may includeaffordances 1424 and 1426 that, when selected, allow a user to changedefault values of additional configuration parameters that the user wasnot prompted to set and/or confirm during the initial configurationsequence.

In the descriptions above, device 600 has been referred to as the“device” and external device 850 has been referred to as the “externaldevice.” However, it should be recognized that external device 850 canbe referred to as a “device” and device 600 can be referred to as an“external device”. For example, from the perspective of external device850, device 600 is an external device.

FIG. 15 is a flow diagram illustrating process 1500 for pairing anelectronic device with an external device. Process 1500 may be performedat an electronic device with a display and a camera, like device 100(FIG. 1), device 300 (FIG. 3), and device 500 (FIG. 5). In oneembodiment, process 1500 is performed by an iPhone® or a smartphone(e.g., 850) to pair the phone to an external device such as a wearableelectronic device (e.g., 600).

Process 1500 provides an intuitive way to set up an electronic device.The method reduces the cognitive burden on a user when pairing anelectronic device with another electronic device, thereby creating amore efficient human-machine interface. For battery-operated computingdevices, enabling a user to set up a device more quickly and moreefficiently conserves power and increases the time between batterycharges.

At block 1502, a wireless communications pairing mode for pairing theelectronic device (e.g., 850) with an external device (e.g., 600) isinvoked. At block 1504, an image is obtained via the camera. The imagecontains a pattern (e.g., 804) displayed on a display screen (e.g., 800)of the external device and the pattern comprises identifying informationof the external device. At block 1506, data is received from theexternal device. At block 1508, a determination is made whether thereceived data corresponds with the identifying information. At block1510, in response to a determination that the received data correspondswith the identifying information, the external device is registered as apaired device.

FIG. 16 is a flow diagram illustrating process 1600 for pairing anelectronic device with an external device. Process 1600 may be performedat an electronic device with a display and a camera, like device 100(FIG. 1), device 300 (FIG. 3), and device 500 (FIG. 5). In oneembodiment, process 1600 is performed by an iPhone® or a smartphone(e.g., 850) to pair the phone to an external device such as a wearableelectronic device (e.g., 600).

Process 1600 provides an intuitive way to set up an electronic device.The method reduces the cognitive burden on a user when pairing anelectronic device with another electronic device, thereby creating amore efficient human-machine interface. For battery-operated computingdevices, enabling a user to set up a device more quickly and moreefficiently conserves power and increases the time between batterycharges.

At block 1602, a wireless communications pairing mode for pairing theelectronic device (e.g., 850) with an external device (e.g., 600) isinvoked, where the pairing mode is initially in a first state in whichthe electronic device will not pair with the external device. At block1604, an image is obtained via the camera, where the image contains apattern (e.g., 804) displayed on a display screen (e.g., 800) of theexternal device. At block 1606, a determination is made whether thefirst pattern corresponds with a predetermined pattern. At block 1608,in response to a determination that the first pattern corresponds with apredetermined pattern, the pairing mode is set to a second state inwhich the electronic device will pair with the external device. At block1610, data is received from the external device. At block 1612, inresponse to receiving the data from the external device, the externaldevice is registered as a paired device.

FIG. 17 is a flow diagram illustrating process 1700 for pairing anelectronic device with an external device. Process 1700 may be performedat an electronic device with a display and a camera, like device 100(FIG. 1), device 300 (FIG. 3), and device 500 (FIG. 5). In oneembodiment, process 1700 is performed by an iPhone® or a smartphone(e.g., 850) to pair the phone to an external device such as a wearableelectronic device (e.g., 600).

Process 1700 provides an intuitive way to set up an electronic device.The method reduces the cognitive burden on a user when pairing anelectronic device with another electronic device, thereby creating amore efficient human-machine interface. For battery-operated computingdevices, enabling a user to set up a device more quickly and moreefficiently conserves power and increases the time between batterycharges.

At block 1702, a wireless communications pairing mode for pairing theelectronic device (e.g., 850) with an external device (e.g., 600) isinvoked. At block 1704, data is received from the external device. Atblock 1706, movement indicative of a physical contact at the electronicdevice is detected. At block 1708, in response to receiving the data anddetecting the movement, the external device is registered as a paireddevice.

FIG. 18 is a flow diagram illustrating process 1800 for setting aconfiguration parameter of an external wearable electronic device.Process 1800 may be performed at an electronic device with a display anda touch-sensitive surface on the display, like device 100 (FIG. 1),device 300 (FIG. 3), and device 500 (FIG. 5). In one embodiment, process1800 is performed by an iPhone® or a smartphone (e.g., 850).

Process 1800 provides an intuitive way to set up an electronic device.The method reduces the cognitive burden on a user when configuring theelectronic device, thereby creating a more efficient human-machineinterface. For battery-operated computing devices, enabling a user toset up a device more quickly and more efficiently conserves power andincreases the time between battery charges.

At block 1802, a configuration interface (e.g., 1110) for configuring anorientation in which a wearable electronic device (e.g., 600) with anasymmetric geometry is to be worn is displayed. At block 1804, a userselection of the orientation is detected. In some embodiments (e.g.,touchscreen embodiments), the device that is performing process 1800 hasa touch screen display and a touch-sensitive surface is on the display.In some embodiments (e.g., non-touchscreen embodiments), the device hasa display separate from the touch-sensitive surface. The exact userinput used to select the orientation during block 1802 may also bedifferent. For example, in touchscreen embodiments, a displayedaffordance (e.g., 1114, 1115, 1116, 1117) associated with theorientation may be responsive to touch input using a touch object, suchas a tap, a long-duration touch, a flick, a swipe, or another applicabletouch-based gesture. In non-touchscreen embodiments, the displayedaffordance may be responsive to mouse events generated using a mouse orequivalent input device, such as a click, double click, drag, and soforth. Combinations of the embodiments are possible. For example, atouchscreen device can be responsive to an external wireless mouse, thusdevices in the touchscreen embodiments can also be responsive to mouseand mouse cursor input techniques. Likewise, a non-touchscreen devicecan be responsive to a touch-sensitive surface (e.g., touchpad), thusdevices of the non-touchscreen embodiments can also be responsive totouch input.

At block 1806, data representing the selected orientation is sent to thewearable electronic device (e.g., 600), where the selected orientationcorresponds to a display orientation of the wearable electronic device.Optionally, (1) the configuration interface comprises a first setting(e.g., 1114, 1115, 1116, 1117) representing a first orientation and asecond setting (e.g., 1114, 1115, 1116, 1117) representing a secondorientation, (2) a selection of the first orientation corresponds to afirst display orientation of the wearable electronic device, and (3) aselection of the second orientation corresponds to a second displayorientation of the wearable electronic device, where the second displayorientation is rotated 180 degrees related to the first displayorientation.

FIG. 19 is a flow diagram illustrating process 1900 for displaying apersonalized message on the display of an electronic device. Process1900 may be performed at an electronic device with a display andtouch-sensitive screen, like device 100 (FIG. 1), device 300 (FIG. 3),and device 500 (FIG. 5). The electronic device may be configured toinitiate a device configuration sequence upon power-on. In oneembodiment, process 1900 is performed by an iPhone® or a smartphone(e.g., 850). In another embodiment, process 1900 is performed by awearable electronic device (e.g., 600).

Process 1900 provides a personalized experience upon set up of anelectronic device. The method may limit the display of a personalizedmessage to appear only during an initial configuration of the device,thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to set up a devicemore quickly and more efficiently conserves power and increases the timebetween battery charges.

At block 1902, a personalized electronic message (e.g., 614) is stored,where the electronic message is stored before an initial deviceconfiguration of the electronic device. At block 1904, a userinstruction to power-on the electronic device is detected. At block1906, a determination is made whether the device configuration sequencehas previously been initiated or completed. At block 1908, in responseto a determination that the device configuration sequence has notpreviously been initiated or completed, the electronic message (e.g.,614) is displayed upon power-on of the electronic device. At block 1910,the device configuration sequence is initiated. At block 1912, a userinterface screen for device configuration (e.g., 700, 710, 800, 900,1100, 1200) is displayed.

FIG. 20 is a flow diagram illustrating process 2000 for setting up anelectronic device. Process 2000 may be performed at an electronic devicewith a touch-sensitive display, like device 100 (FIG. 1), device 300(FIG. 3), and device 500 (FIG. 5). In one embodiment, process 2000 isperformed by a wearable electronic device (e.g., 600). Setup of thewearable electronic device according to process 2000 may include pairingwith an external device such as an iPhone® or other smartphone (e.g.,850).

Process 2000 provides an intuitive way to set up an electronic device.The method reduces the cognitive burden on a user when configuring thedevice and pairing it with another device, thereby creating a moreefficient human-machine interface. For battery-operated computingdevices, enabling a user to set up a device more quickly and moreefficiently conserves power and increases the time between batterycharges.

At block 2002, at least one device initialization screen (e.g., 602,606, 612) is displayed on the touch-sensitive display of the device. Atblock 2004, an instruction screen (e.g., 800, 900) is displayedinstructing a user to pair an external device with the electronicdevice. At block 2006, first data is sent via wireless communication. Atblock 2008, a pattern (e.g., 804) comprising identifying information ofthe electronic device is displayed. At block 2010, second dataindicating that the external device and the electronic device have beenpaired using the first data is received. At block 2012, an aural orhaptic indication that the electronic device and the external devicehave been paired is provided.

It should be understood that the particular order in which theoperations in FIGS. 15-20 have been described is exemplary and notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.For brevity, these details are not repeated here. Additionally, itshould be noted that aspects of processes 1500-2000 (FIGS. 15-20) may beincorporated with one another.

The operations in the information processing methods described above maybe implemented by running one or more functional modules in informationprocessing apparatus such as general purpose processors or applicationspecific chips. These modules, combinations of these modules, and/ortheir combination with general hardware (e.g., as described above withrespect to FIGS. 1A, 1B, 3, 5A, and 5B) are all included within thescope of protection of the invention.

FIG. 21 shows exemplary functional blocks of an electronic device 2100that, in some embodiments, performs the above-described features. Asshown in FIG. 21, an electronic device 2100 may include display unit2102 configured to display graphical objects; human input interface unit2104 configured to receive user input; one or more RF units 2106configured to detect and communicate with external electronic devices;one or more feedback unit configured to provide user with haptic, audio,and/or visual feedback; and processing unit 2110 coupled to display unit2102, human input interface unit 2104, RF unit(s) 2106, and feedbackunit 2108. In some embodiments, processing unit 2110 is configured tosupport an operating system running on operating system unit 2112. Inturn, operating system unit 2112 may support an applications unit 2114for launching and running one or more applications.

In some embodiments, the processing unit 2110 includes a displayenabling unit 2116 and a setup management unit 2118. In someembodiments, the display enabling unit 2116 is configured to cause adisplay of a user interface (or portions of a user interface) inconjunction with the display unit 2102. For example, the displayenabling unit 2116 may be used for displaying screens during setup. Insome embodiments, the setup management unit 2118 is configured toreceive input, e.g., through the use of human input interface unit 2104and/or RF unit 2106 and to perform the setup and device configurationfeatures described above.

In some embodiments, RF unit 2106 is configured to detect and receiveinformation from an external device, such as information forfacilitating the pairing and configuration of the receiving device, userinformation, application information, application state information, soforth. In some embodiments, the RF unit is configured to detect andtransmit information to an external device, such as information forfacilitating the pairing and configuration of the receiving device, userinformation, application information, application state information, soforth.

The units of FIG. 21 may be used to implement the various techniques andmethods described above with respect to FIGS. 6-20. The units of device2100 are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described examples. It is understood by persons of skill in theart that the functional blocks described in FIG. 21 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described examples. Therefore, the description herein optionallysupports any possible combination or separation or further definition ofthe functional blocks described herein.

In accordance with some embodiments, FIG. 22 shows a functional blockdiagram of an electronic device 2200 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the function blocks described in FIG. 22 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 22, an electronic device 2200 includes a camera unit2202 configured to obtain images, and a processing unit 2204 coupled tothe camera unit 2202. In some embodiments, the processing unit 2204optionally includes an invoking unit 2206, a camera enabling unit 2208,a receiving unit 2210, a determining unit 2212, a registering unit 2214,and a comparing unit 2216.

The processing unit 2204 is configured to invoke (e.g., with invokingunit 2206) a wireless communications pairing mode for pairing theelectronic device with an external device, and enable (e.g., with cameraenabling unit 2208) obtaining of an image via the camera unit 2202, theimage containing a pattern displayed on a display screen of the externaldevice, the pattern comprising identifying information of the externaldevice. The processing unit 2210 is further configured to receive (e.g.,with receiving unit 2210) data from the external device, determine(e.g., with determining unit 2212) whether the received data correspondswith the identifying information, and, in response to a determinationthat the received data corresponds with the identifying information,register (e.g., with registering unit 2214) the external device as apaired device.

In some embodiments, the received data includes data indicative of thepattern displayed on the external device. In some embodiments,determining whether the received data corresponds with the identifyinginformation includes comparing (e.g., with comparing unit 2216) the dataindicative of the pattern against the pattern in the image.

The operations described above with reference to FIG. 15 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.22. For example, invoking operation 1502, obtaining operation 1504,receiving operation 1506, determining operation 1508, and registeringoperation 1510 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 23 shows a functional blockdiagram of an electronic device 2300 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the function blocks described in FIG. 23 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 23, an electronic device 2300 includes a camera unit2302 configured to obtain images and a processing unit 2304 coupled tothe camera unit 2302. In some embodiments, the processing unit 2304optionally includes an invoking unit 2306, a camera enabling unit 2308,a determining unit 2310, a setting unit 2312, a receiving unit 2314, anda registering unit 2316.

Processing unit 2304 is configured to invoke (e.g., with invoking unit2306) a wireless communications pairing mode for pairing the electronicdevice with an external device, where the pairing mode is initially in afirst state in which the electronic device will not pair with theexternal device. The processing unit 2304 is further configured toenable (e.g., with camera enabling unit 2308) obtaining of an image viathe camera unit, the image containing a first pattern displayed on adisplay screen of the external device, and determine (e.g., withdetermining unit 2310) whether the first pattern corresponds with apredetermined pattern. The processing unit 2304 is further configuredto, in response to a determination that the first pattern correspondswith the predetermined pattern, set (e.g., with setting unit 2312) thepairing mode to a second state in which the electronic device will pairwith the external device, receive (e.g., with receiving unit 2314) datafrom the external device, and, in response to receiving the data fromthe external device, register (e.g., with registering unit 2316) theexternal device as a paired device. In some embodiments, the imagecontains a visual representation of the external device.

The operations described above with reference to FIG. 16 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.23. For example, invoking operation 1602, obtaining operation 1604,determining operation 1606, setting operation 1608, receiving operation1610, and registering operation 1612 are, optionally, implemented byevent sorter 170, event recognizer 180, and event handler 190. Eventmonitor 171 in event sorter 170 detects a contact on touch-sensitivedisplay 112, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether a first contact at a firstlocation on the touch-sensitive surface (or whether rotation of thedevice) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 24 shows a functional blockdiagram of an electronic device 2400 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the function blocks described in FIG. 24 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 24, an electronic device 2400 includes a processingunit 2402. In some embodiments, the processing unit 2402 optionallyincludes an invoking unit 2404, receiving unit 2406, detecting unit2408, registering unit 2410, send enabling unit 2412, aural indicationenabling unit 2414, and haptic indication enabling unit 2416.

Processing unit 2402 is configured to invoke (e.g., with invoking unit2404) a wireless communications pairing mode for pairing the electronicdevice with an external device, receive (e.g., with receiving unit 2406)data from the external device, detect (e.g., with detecting unit 2408)movement indicative of a physical contact at the electronic device, andin response to receiving the data and detecting the movement, register(e.g., with registering unit 2410) the external device as a paireddevice.

In some embodiments, processing unit 2402 is further configured to,after registering the external device as a paired device, enable (e.g.,with send enabling unit 2412) sending of user information from theelectronic device to the external device. In some embodiments, the userinformation comprises WiFi settings, contact information of usercontacts, identification of an installed application, or servicesettings.

In some embodiments, the processing unit 2402 is further configured to,after registering the external device as a paired device, enable (e.g.,with aural indication enabling unit 2414 or haptic indication enablingunit 2416), at the electronic device, an aural or haptic indication thatthe electronic device and the external device are paired.

In some embodiments, the wireless communications pairing mode includesan activation of a pairing application program configured to be invokedby a user selection of a user interface object displayed on a displayunit of the electronic device, where the user interface object isassociated with the pairing application.

In some embodiments, the user interface object associated with thepairing application is available for user selection only when theexternal device is within communication range of the electronic device.In some embodiments, the external device is a wearable electronic devicethat, optionally, includes a rotatable input mechanism.

The operations described above with reference to FIG. 17 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.24. For example, invoking operation 1702, receiving operation 1704,determining operation 1508, detecting operation 1706, and registeringoperation 1708 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 25 shows a functional blockdiagram of an electronic device 2500 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the function blocks described in FIG. 25 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 25, an electronic device 2500 includes atouch-sensitive surface unit 2502 configured to receive contacts, adisplay unit 2504 optionally coupled to the touch-sensitive surface unit2502 and configured to display a graphic user interface, and aprocessing unit 2506 optionally coupled to the touch-sensitive surfaceunit 2502 and the display unit 2504. In some embodiments, the processingunit 2506 optionally includes a display enabling unit 2508, detectingunit 2510, and a send enabling unit 2512. In some embodiments, theelectronic device is a smartphone.

Processing unit 2506 is configured to enable (e.g., with displayenabling unit 2508) display of a configuration interface for configuringan orientation in which a wearable electronic device with an asymmetricgeometry is to be worn, detect (e.g., with detecting unit 2510) a userselection of the orientation, and enable (e.g., with send enabling unit2512) sending data representing the selected orientation to the wearableelectronic device, where the selected orientation corresponds to adisplay orientation of the wearable electronic device.

In some embodiments, the configuration interface includes a firstsetting representing a first orientation and a second settingrepresenting a second orientation, a selection of the first orientationcorresponds to a first display orientation of the wearable electronicdevice, and a selection of the second orientation corresponds to asecond display orientation of the wearable electronic device, where thesecond display orientation is rotated 180 degrees related to the firstdisplay orientation.

In some embodiments, the wearable electronic device includes a rotatableinput mechanism. In some embodiments, a selection of the firstorientation causes the wearable electronic device to scroll-downdisplayed information in response to a clockwise rotation of therotatable input mechanism. In some embodiments, a selection of thesecond orientation causes the wearable electronic device to scroll-updisplayed information in response to a clockwise rotation of therotatable input mechanism.

In some embodiments, processing unit 2206 is further configured toenable (e.g., with display enabling unit 2508) display of aconfiguration interface for selecting a clock face among a plurality ofclock faces, detect (e.g., with detecting unit 2510) a user selection ofthe clock face, and enable (e.g., with send enabling unit 2512) sendingof data to the wearable electronic device that causes the wearableelectronic device to display the current time using the selected clockface.

The operations described above with reference to FIG. 18 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.25. For example, display enabling operation 1802, detecting operation1804, and sending operation 1806 are, optionally, implemented by eventsorter 170, event recognizer 180, and event handler 190. Event monitor171 in event sorter 170 detects a contact on touch-sensitive display112, and event dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 26 shows a functional blockdiagram of an electronic device 2600 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the function blocks described in FIG. 26 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 26, an electronic device 2600 includes a display unit2602 configured to graphic user interface, and a processing unit 2604coupled to the display unit 2602. In some embodiments, the processingunit 2604 optionally includes a storing unit 2606, a detecting unit2608, a determining unit 2610, a display enabling unit 2612, aninitiating unit 2614, and a receiving unit 2616.

Processing unit 2604 is configured to store (e.g., with storing unit2606) a personalized electronic message, where the electronic message isstored before an initial device configuration of the electronic device.Processing unit 2604 is further configured to detect (e.g., withdetecting unit 2608) a user instruction to power-on the electronicdevice, determine (e.g., with determining unit 2610) whether the deviceconfiguration sequence has previously been initiated or completed, and,in response to a determination that the device configuration sequencehas not previously been initiated or completed, enable (e.g., withdisplay enabling unit 2612) display of the electronic message uponpower-on of the electronic device. Processing unit 2604 is furtherconfigured to, after enabling display of the electronic message,initiate (e.g., with initiating unit 2614) the device configurationsequence, and enable (e.g., with display enabling unit 2612) display ofa user interface screen for device configuration.

In some embodiments, display of the electronic message is not enabledagain upon power-on after completion of the initial deviceconfiguration. In some embodiments, the electronic device is capable ofbeing reset as though the device configuration sequence has notpreviously been initiated or completed.

In some embodiments, the electronic message is personalized to anintended user of the electronic device. In some embodiments, theprocessing unit is further configured to receive (e.g., with receivingunit 2616) the personalized electronic message from apoint-of-sale-device. In some embodiments, the electronic device is awearable electronic device.

The operations described above with reference to FIG. 19 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.26. For example, storing operation 1902, detecting operation 1904,determining operation 1906, display enabling operations 1908 and 1912,and initiating operation 1910 are, optionally, implemented by eventsorter 170, event recognizer 180, and event handler 190. Event monitor171 in event sorter 170 detects a contact on touch-sensitive display112, and event dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 27 shows a functional blockdiagram of an electronic device 2700 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the function blocks described in FIG. 27 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 27, an electronic device 2700 includes atouch-sensitive surface unit 2702 configured to receive contacts, adisplay unit 2704 optionally coupled to the touch-sensitive surface unit2702 and configured to display a graphic user interface, and aprocessing unit 2206 optionally coupled to the touch-sensitive surfaceunit 2702 and the display unit 2704. In some embodiments, the processingunit 2706 optionally includes a display enabling unit 2708, a sendenabling unit 2710, a receiving unit 2712, an aural indication enablingunit 2714, and a haptic indication enabling unit 2716.

Processing unit 2706 is configured to enable (e.g., with displayenabling unit 2708) display of at least one device initializationscreen, and, after enabling display of the at least one deviceinitialization screen, enable (e.g., with display enabling unit 2708)display of an instruction screen instructing a user to pair the externaldevice with the electronic device, enable (e.g., with send enabling unit2710) sending of first data via wireless communication, enable (e.g.,with display enabling unit 2708) display of a pattern comprisingidentifying information of the electronic device, and receive (e.g.,with receiving unit 2712) second data indicating that the externaldevice and the electronic device have been paired using the first data.Processing unit 2706 is further configured to, after receiving thesecond data, enable (e.g., with aural indication enabling unit 2714 orhaptic indication enabling unit 2716) an aural or haptic indication thatthe electronic device and the external device have been paired. In someembodiments, the instruction screen includes an instruction instructingthe user to capture an image of the displayed pattern using the externaldevice.

In some embodiments, the processing unit is further configured to enable(e.g., with display enabling unit 2708) display of a home screen afterreceiving the second data. In some embodiments, the home screencomprises a plurality of affordances, which when selected, launchcorresponding applications. Optionally, the home screen comprises adisplay of the current time.

In some embodiments, processing unit 2706 is further configured to,before displaying the home screen, enable (e.g., with display enablingunit 2708) display of a screen configured to allow a user to select aclock face for the electronic device.

In some embodiments, processing unit 2706 is further configured to,before displaying the home screen, enable (e.g., with display enablingunit 2708) display of a screen configured to allow a user to select anorientation in which the electronic device is to be worn by the user.

In some embodiments, processing unit 2706 is further configured to,before displaying the home screen, enable (e.g., with display enablingunit 2708) display of a screen configured to allow a user to select oneor more services to be made accessible to the electronic device.

In some embodiments, processing unit 2706 is further configured to,after receiving confirmation that the external device and the electronicdevice have been paired, receive (e.g., with receiving unit 2712) userinformation from the external device. In some embodiments, the userinformation includes WiFi settings, contact information of usercontacts, identification of an installed application, or services. Insome embodiments, the at least one device initialization screen includesat least one of a boot-up screen, a welcome screen, and apersonalized-message screen.

In some embodiments, the electronic device is a wearable electronicdevice. In some embodiments, the electronic device includes a rotatableinput mechanism. In some embodiments, the external device is asmartphone.

The operations described above with reference to FIG. 20 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.27. For example, display enabling operations 2002, 2004, and 2008,sending operation 2006, receiving operation 2010, and providingoperation 2012 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best utilize the invention andvarious embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. An electronic device, comprising: atouch-sensitive display; one or more processors; and memory storing oneor more programs configured to be executed by the one or moreprocessors, the one or more programs including instructions for:displaying a configuration interface for configuring an orientation inwhich a wearable electronic device with an asymmetric geometry is to beworn; detecting a user selection of the orientation; and sending datarepresenting the selected orientation to the wearable electronic device,wherein: the selected orientation corresponds to a display orientationof the wearable electronic device.
 2. The electronic device of claim 1,wherein the configuration interface comprises a first settingrepresenting a first orientation and a second setting representing asecond orientation, wherein a selection of the first orientationcorresponds to a first display orientation of the wearable electronicdevice, and wherein a selection of the second orientation corresponds toa second display orientation of the wearable electronic device, whereinthe second display orientation is rotated 180 degrees related to thefirst display orientation.
 3. The electronic device of claim 2, whereinthe wearable electronic device includes a rotatable input mechanism. 4.The electronic device of claim 3, wherein a selection of the firstorientation causes the wearable electronic device to scroll-downdisplayed information in response to a clockwise rotation of therotatable input mechanism.
 5. The electronic device of claim 3, whereina selection of the second orientation causes the electronic device toscroll-up displayed information in response to a clockwise rotation ofthe rotatable input mechanism.
 6. The electronic device of claim 1,wherein the one or more programs store instructions for: displaying aconfiguration interface for selecting a clock face among a plurality ofclock faces; detecting a user selection of the clock face; and sendingdata to the wearable electronic device that causes the wearableelectronic device to display the current time using the selected clockface.
 7. The electronic device of claim 1, wherein the electronic deviceis a smartphone.
 8. A method, comprising: at an electronic device with atouch-sensitive display, displaying a configuration interface forconfiguring an orientation in which a wearable electronic device with anasymmetric geometry is to be worn; detecting a user selection of theorientation; and sending data representing the selected orientation tothe wearable electronic device, wherein: the selected orientationcorresponds to a display orientation of the wearable electronic device.9. A non-transitory computer-readable storage medium storing one or moreprograms configured to be executed by one or more processors of anelectronic device with a touch-sensitive display, the one or moreprograms including instructions for: displaying a configurationinterface for configuring an orientation in which a wearable electronicdevice with an asymmetric geometry is to be worn; detecting a userselection of the orientation; and sending data representing the selectedorientation to the wearable electronic device, wherein: the selectedorientation corresponds to a display orientation of the wearableelectronic device.